Generate Campaign Test History setting

Administrators can activate a setting that creates a test history contact table when a user tests a campaign. This table is a mirror of the actual contact history table, and can be used for reporting prior to running the live campaign.

Test history contact tables are for reporting purposes only and are not supported for use in audience or cell segmentation.

When you are using Test Mode to send emails to a small number of recipients, and/or output records, this will not limit what is populated into the test history contact table. The test history contact table will always contain data relating to the full audience.

Before you begin

Be aware of the following important notes before you configure this setting:

Procedure

1. In the Settings > Datasources screen, under the General tab, click the Edit button.
2. In the Generate Campaign Test History field type 'true'.
3. When a user runs a campaign in test mode, the Generate Campaign History check box must be selected in the campaign Overview tab for the campaign test history contact table to be created.
4. If you change the setting from 'true' to 'false' at a later stage, any existing test history contact tables will not be affected.

Results

When a user test runs a campaign, with the Generate Campaign Test History setting set to 'true' and the Generate Campaign History check box selected in the Campaign Manager Overview tab, a test campaigns history contact table is created. The table is named 'Test_' + the campaign history contact table name, and it is visible in the Campaign Manager Data Explorer pane.

The table will contain data for every test run of every campaign since the table was cleared as part of the nightly data update process. Data is appended to the table every time a test is run.

Clearing a test does not automatically delete the test history contact table. If required, the table can be cleared down as part of the nightly data update process using the iLoader DROP command. Alternatively you can delete the table at any time using the AMC Engine Repository applet. The table is recreated the next time a user test runs a campaign.

• Datasources
  • Prerequisites for creating and configuring Datasources
  • Adding an Engine Datasource
  • Generate Campaign Test History Setting
  • Editing an Existing Datasource
  • Disabling or Enabling a Datasource
  • Allocating Campaign Settings to an Engine Datasource
  • Configuring Access Permissions to a Datasource
  • Applying Engine Row and Column Permissions
  • Setting Engine Security